Purpose

Fixes:
ballerina-platform/ballerina-library#8354

Fixed issues:

• Previous implementation has the following issues and fixed with the new design,
  • Using complex and duplicated analysis to get argument values with parameter names
  • Does not use semantic information to resolve module name to filter the crypto module function
  • Using semantic model references API to check whether the value is modified. But this is not ideal since if the variable is even used without reassignment or modification, it can be referenced. Ideal solution would be navigate to the references and check the nodes. But this is a very complex process. Hence, used an analysis based on the global and local block scopes to find the modifications or reassignments. Yet, any blocks like if, match, etc. can change the values, so avoided to resolve the variable declaration finding if we encounter any block statements. This is the least intrusive option.
• With the new implementation, a new interface is introduce to implement any resource level static code rules and a context object is introduced which can contain all the required objects to perform the analysis
• Fixes several other bugs in the previous implementation
• Added a section in the specification regarding the static code rules. The section follows the following format:

  # Static Rule Title
  
  <!-- one line description of the static code rule -->
  
  ## Why this is an issue?
  
  ## What is the potential impact?
  
  ## How can I fix this?
  
  <!-- description -->
  
  **Non-complaint code:**
  <!-- code example -->
  
  **Complaint code:**
  <!-- code example -->
  
  ## Additional Resources

• Removed the rule 4. Check the comment in the issue for more information. Also IMO suggesting to use a external method call might not looks nice. We should consider this when we can a Ballerina level support for creating secure randoms

Examples

N/A

Checklist

• Linked to an issue
• Updated the changelog
• Added tests
• Updated the spec
• Checked native-image compatibility